Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prioritize pods on unschedulable nodes #53

Merged
merged 2 commits into from
Apr 30, 2019
Merged

Conversation

mikkeloscar
Copy link
Collaborator

This is an optimization to prioritize pods on nodes which are marked
unschedulable higher than pods on schedulable nodes. Unschedulable nodes
indicate that the node is being drained, so it makes sense to move those
pods as soon as possible.

This is an optimization to prioritize pods on nodes which are marked
unschedulable higher than pods on schedulable nodes. Unschedulable nodes
indicate that the node is being drained, so it makes sense to move those
pods as soon as possible.

Signed-off-by: Mikkel Oscar Lyderik Larsen <mikkel.larsen@zalando.de>
@otrosien
Copy link
Member

👍

@@ -506,12 +506,12 @@ func (o *Operator) getPodToUpdate(pods []v1.Pod, sts *appsv1.StatefulSet, sr Sta
return nil, nil
}

prioritizedNodes, err := o.getPrioritizedNodes()
prioritizedNodes, cordonedNodes, err := o.getNodes()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wouldn't it make sense to unify the naming cordoned vs. unschedulable?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, changed it to unscheduled midway through the change, forgot to change this variable..

Signed-off-by: Mikkel Oscar Lyderik Larsen <mikkel.larsen@zalando.de>
@mikkeloscar
Copy link
Collaborator Author

👍

1 similar comment
@otrosien
Copy link
Member

👍

@otrosien otrosien merged commit 1b313a0 into master Apr 30, 2019
@otrosien otrosien deleted the unschedulable-nodes branch April 30, 2019 08:15
@otrosien otrosien added this to the v0.2.0 milestone May 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants